home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Arsenal Files 8
/
The Arsenal Files Collection #8 (Arsenal Computer) (1996).ISO
/
telecom
/
ezpro10.zip
/
EPROMISC.DOC
< prev
next >
Wrap
Text File
|
1996-10-01
|
22KB
|
559 lines
EPROMISC is EZYPRO' utility function program. It contains many
utility functions which are not stored within EZYPRO.EXE.
EPROMISC is included to extended the functionality of EZYPRO
to make it a complete utility package for the Ezycom sysop that
not only provides BBS related functions, but also those for the
mailers that the Ezycom sysops run. That is: it is a complete
companion tool, not one of many, that you need to manage your
Ezycomn BBS.
These functions are..
/AGE : Create user age graph
/CLEAN : Clean up .ASC files for deleted areas
/DIRS : Create FILES.DIR list of FREQable dirs
/DOOR : Create Door usage graph screens
/ECHOLIST : Create message area echo lists
/FBCLEAN : Filebase cleanup. Delete redundant files
/FDA, /IMA : Generate Frontdoor or Intermail traffic reports
/FDSTRIP : Trim Intermail log file *
/FILDUMP : Dump file base info to text file
/IMSTRIP : Trim Intermail log file *
/INIT : Initialize history files
/LIST : Sends status notification messages to nodes
/MBCLEAN : Message area clean up. Remove redundant
message areas *
/MSGDUMP : Dump message base info to text file
/NEWS : Create ANS/ASC news files
/POINT : Create top 15 filepoints screen
/PURGE : Purge news articles
/SCAN : Generate filebase analysis report
/STATn : Generate statistics screens sorted by n, (n=1-5)
/TRIM : Trim log file to days specified on control file
/U=<user> : Create list of files uploaded by xxxx
/UPEXPORT : Export upload list to a text file
/VIEW : Display list of files uploaded from last /U
Functions listed with the * at the end are not currently
available in this beta release of the package.
I am currently seeking to add functions to analyse Binkley and
D'Bridge log files. If anyone has a log file for one of these
mailers I'd be pleased to accept one and I'll include some
D'Bridge and Binkley traffic and trim functions in the next
release.
If you have other suggestions, comments or needs please feel
free to send them to :
Phillip Morgan, Internet: pm@tbt.dialix.oz.au
P.O. Box 449 Fidonet: 3:639/252
Croydon, Vic 3136 Ezynet: 151:6133/101
/AGE
This functionproduces a horizintal graph that shows the
percentage of your total user base for 12 age groups. The
youngest group lists users for ages 11 - 20, but users under 11
years of age will be included in that group.
To create this graph type EPROMISC /AGE. The resulting ANS/ASC
files will be placed in the textfiles directory as specified in
your EZYPRO configuration.
The maximum percentage of any category is 35%.
/CLEAN
Depending on how you delete your file areas you may have area
headers lying around that are just taking up space (albeit, only
a little space). This function searches through your Ezycom file
base defintions and locates all area headers for areas that are
no longer defined and asks you if you wish to delete them.
This function displays the area numbers and names as it reads
the file base definitions. When it find a header for an
undefined area you are asked "Found but path is blank --->
Delete it? (Y/n/a):"
The options are Y = Yes, delete the header, N = No leave it
alone, A = Abort the run.
To Run this function type EPROMISC /CLEAN.
/DIRS
This function creates a list of directories from your Ezycom
file base and writes those names to a file called FILES.DIR
which can be used by other programs such as mailers for a list
of freqable directories.
To run this function type EPROMISC /DIRS
/DOOR
This function creates the door usage graph. In order for this
function to work you must be collecting door usage data using
the EZYTDOOR program (and its /P command).
Two files are created.. DOORGRPH.ANS and DOORGRPH.ASC, and these
are placed in your text files directory as specified in your
EZYPRO configuration.
The graph is a scalable graph. The door with the highest number
of calls is set as the maximum margin for the graph and all
other doors are scaled against that maximum.
/ECHOLIST
You can abbreviate this one to /ECHO.
Use this function to create a list of message areas defined on
your Ezycom system. Two files are created. The first is a sorted
list of message area tags. The second is a list of tags and
descriptions.
The first list is useful for downlinks who want to perform area
maintenance, and the second list gives your downlinks an idea of
the message areas topic on your system.
The file name is configured via the EZYPRO configuration
program and the extensions .TAG and .LST are added to the files.
If you used the file name of ECHOLIST then the two files that
are created would be called ECHOLIST.TAG and ECHOLIST.LST.
EZYPRO also provides the ability to exclude mesaage areas from
the output list by placing the tag names in another file that
you define in the EZYPRO configuration program. For example,
you might call your file EXCLUDE (the extesnion .CTL is
automatically added to the end). For example, you have an echo
called NEW_ECHO and you don't want that echo listed in your
output files. Simply added the line NEW_ECHO to the Ascii file
and it will be omitted.
/FBCLEAN
File base clean up is an extension to the facilities in Ezycom
file area definitions. Its purpose is simply to give you more
flexibility with file base management.
EZYPRO allows you to specify global controls or controls per
area. The minimum downloads and oldest file parameters on the
first page of the configuration program are the global override
controls. If set to zero the individual area controls are used.
Ezycom provides for deleting files that arrived nn days ago,
have not been downloaded in nn days or files that are nn days
old. EZYPRO adds the ability to download files that have been
downloaded fewer than a specified number of times in a given
period and provides the ability to move the files to another
directory for checking prior to being deleted.
This function also provides a test function which allows you to
determine the impact of running a filebase cleanup given the
controls you have specified and provides extensive file base
analysis information such as amount of disk space regained from
the cleanup process.
When file moving is enabled (registered version only), the
/FBCLEAN function will watch disk space as it moves the files.
If you run out of space on the drive where files are being moved
to the process will terminate.
The /FBCLEAN process in EZYPRO does not use the date of the
file as specified in the filebase, as this may be wrong (If you
don't run EZYFILE -UPDATE after changing or touching a file), so
the real file date is used.
Results of the /FBCLEAN process are written to a file called
EYCLEAN.RES.
Please note that at the current beta release this function has
been disabled whilst the function is re-written from scratch.
/FDA, /IMA
These functions both do the same thing, except that one works
with the Frontdoor log file, the other works with the Intermail
Log file.
Two files are created by this function. The first is a summary
file called MAILSUM.TXT, which contains a summary list of
transfers from specified addresses. The second file is called
MAILNODE.TXT and is the list of transactions for the requested
address. All transactions from the log file for the address are
listed individually and summarised at the end with total number
and size of file sent and received and an average CPS rate for
those transfers.
EPROMISC /xMA requires one other parameter: The address to be
reported on. For example, you would run this function thus...
EPROMISC /IMA 3:639/252 or EPROMISC /FDA 3:639/252
You will need to run this function for each address you wish to
analyse.
On my system I have my maintenance set up to move my log files
on the first of each month. After that some batch commands are
run to analyse the previous months transactions for each of the
downlinks from my system. Since I run two lines this process is
repeated for each line I run and I then end up with a report
that I could send to each node of transfers for the previous
month.
I also have a summary file listing the totals for each address
for the previous month which quickly enables me to identify
where the flow of files and mail is going. This simplfies set up
of polling schedules, identifying who takes what, which nodes
are getting good connects (eg high CPS rates), how much data is
flowing through my system, and on which lines so I have a clear
picture of how my system is performing.
With that knowledge I can do capacity planning, availability and
recovery planning and be reasonably confident that when I go
away the system will keep on going (provided I acted upon what I
was being presented in the analysis reports). Well, except for
the large volume of corrupt files that typically come from a
very few file areas on the assorted file backbones.
Currently, they expect to find the log file in the current
directory (Either you are logged into the directory where they
files are or they are in the same directory as the EPROMISC.EXE
program.
/FDSTRIP, /IMSTRIP
These functions are similar to the /IMA and /FDA functions in
that both /FDSTRIP and /IMSTRIP do the same thing: They trim the
Frontdoor and Intermail log files to the number of days you
specified on EZYPRO' configuration. They look for the log
files FD.LOG and IM.LOG respectively.
Currently, they expect to find the log file in the current
directory (Either you are logged into the directory where they
files are or they are in the same directory as the EPROMISC.EXE
program.
Future versions of EZYPRO will provide the ability to specify
the file name on the command line.
/FILDUMP
This function creates an Ascii file that contain a list of all
available file area defintions on your BBS. Undefined areas are
listed as "-" in the area name.
The output file is called EZYTFILE.DMP and is created in your
EZYPRO directory.
/INIT
The /INIT function is used to generate fresh history files for
the EZYPRO history generation functions. It needs to be run
whenever you increase the number of file or message areas on
your system.
In preference to increasing those items, set the maximum number
of file and message areas on your BBS to the highest number you
think you will ever be likely to use.
The history file generated are called MSGBASE.HST, FILEBASE.HST
and EZYPRO.HST. The size of the files is dependant on the
reterntion period you specified on the control file (1 - 12
months), and the number of file and message areas on your
system. The following calculations are used to determine the
file sizes...
Filebase Msgbase
Number of areas x (months x 31) x 20 Number of areas x (monthsx 31) x 15
Eg. 400 areas, 12 months retention Eg 1536 areas, 12 months retention
= 400 x (12 x 31) x 20 = 1536 x (12 x 31) x 15
= 2976000bytes = 8570880 bytes
= 2976 kb = 8570 kb
/LIST
Ezycom currently does not provide an automated method of sending
echoarea lists to other systems. The EZYNET -U function can be
used to send a message to a specific address, but what about the
situation where you want to do this for every connected node and
on a regular, periodic basis.
That is what the /LIST function does.
Using a control file called EZYPRO.NOT (short for notify),
EPROMISC will send such messages to all listed systems on the
date listed in the control file.
The control file can be up to 512 lines long and may contain
comments, addresses and a single line which specifies on what
day of the month messages are sent.
The first non-comment line of the control file must be a two
digit number specifying the day to send messages. 01, 10, 20 and
25 are all examples of valid values.
Comments are any lines preceeded by a semi colon (;).
All other lines are considered to be addresses. These addresses
are NOT checked for validity. If you get them wrong you will get
no message telling you that they are wrong. All addresses must
be full 3D or 4D addresses (eg 3:639/252 and 3:639/252.100 are
both valid addresses). Do not include domain names on your
addresses (eg @fidonet).
EPROMISC first checks to see if the day of the month in the
control file matches today. If so, it reads in all the addresses
then simply calls EZYNET -U with the address appended and EZYNET
does the rest.
/MBCLEAN
This function is similar to the /FBCLEAN function in principle
(that it, it cleans up your message base).It is designed to
physically remove message areas from your system that have no
traffic for a specified period of days. The number of days is
specified in the configuration file.
To use this function you must have been using the history
generation functions as this is how /MBCLEAN determines that
there has been no flow in the area.
The message area must not only have had no traffic, but it must
have no messages in it and have no connected systems other than
the uplink system.
This function will also report all areas on your system that
have no messages, have had no flow but do have connected systems
so that you can make a decision on whjat you are going to do
with the area.
/MSGDUMP
This function creates an Ascii file that contain a list of all
available messge area defintions on your BBS. Undefined areas
are listed as "-" in the area name.
The output file is called EZYTMSG.DMP and is created in your
EZYPRO directory.
/NEWS
Ezycom provides the ability to display a news file (which must
be called NEWS.ANS/.ASC), after a user logs on but before the
top menu is displayed.
EZYPRO provides the ability to create news files (of any name,
but Ezycom looks only for NEWS). You can use the editor in
Ezyshell to edit your source news file, or any other text editor.
This first line of this source file must be in the format xx ;
yy ; zz, where xx = the header color, yy = border color and zz
= text color. Here is a sample of the news header...
------------------------------
-----------| This is a test header |----------------| 24/06/96 |----
------------------------------
The header color refers to the text inside the box, the border
color is the box color. The text color is the color of the word
below the header (your actual message).
The EZYPRO news function also allows for comments in your news
file. Preceed lines with a semi colon and they will be treated
as comments.
A comment file may be up to 512 lines long.
After editing your source news file use EPROMISC /NEWS to
generate the .ANS and .ASC news files, which will be placed in
the text files directory specified in the configuration.
The date must be entered as DD-MM-YY, or by uing the macro
*TODAY. *TODAY means use the current system date when creating
the output news file, and will always use the system date
whenever the news file is recreated. Using such a date will
result in an article always being current and ineligible for
purging.
/POINT
One of EZYPRO' many user screens is the FPOINTS screens. Two
screens are created (.ANS and .ASC), and placed in your text
files directory.
This function simply creates a screen containing a list of 15
users with the most file points accrued, in descending order.
/PURGE
With the ability to create news files some means of managing
your news files is also needed.
The configuration program provided a means of entering a
filename, and below that is a parameter which specifies the
retention of the news articles.
A value of 0 disables purging, so articles will always stay on
the .ANS./.ASC screens. If you used the *TODAY macro when
specifying a date on the news article that article will never be
deleted, as today is never greater than the number of days
specified for the retention.
The allowable range for the purge function is 0 to 255 days.
To purge the news articles type EPROMISC /PURGE.
Once the purge has completed EPROMISC will automatically run
EPROMISC /NEWS to regenerate the .ANS/.ASC output files.
/SCAN [Not currently available]
This function produces a filebase analysis report that shows the
following:
The number of users at each of your security levels.
The number of bytes transferrable at a dozen modem speeds based
on 100% efficiency
The smallest, average size and largest files on your system,
by area
The percentage of users at each security level that could
download the smallest, average size and larget files per area
The number of downloads per area vs the total number of and size
of files in those areas
The percentage of your total file base per area
How well each area is performing (Large areas with few downloads
are said to be poor performers).
Having this information simplifies file base management. It
enables you to determine which areas on your BBS are just
wasting disk space. Typically you'll find games and Windows 95
areas are good performers, whilst something like missing persons
and chess base type areas are dead.
/STATn
The /STAT function produces 2 screens containing the top 15
users sorted in one of five sequences. The data on the screens
is the same, but the actuall contents (the users that are
listed), will be dependant upon which of the 5 sequences you
select. The available sequences are...
1. Kilobytes uploaded
2. Kilobytes downloaded (default if no sequence requested).
3. Number of calls
4. Number of messages posted
5. Number of file points accrued.
/TRIM
This function trims your Ezybest log file (not your debug file).
The number of days to retain is specified on the configuration
file.
The EZYPRO log file typically grows at around 1 - 2 kb per
day, so a retention of 21 (three weeks), will give you, at most,
a log file 45 kb in size.
The log file is expected to be found in the log file directory
as specified on page two of the configuration program.
/U=<user>
EZYPRO provides the ability to scan your user base and locate
all files uploaded by <user>. A file called UPLDLIST.DAT is
created in your EZYPRO directory which contains list of all
files uploaded by the named user. You can't view this file with
a text editor. You need to use either EPROMISC /VIEW (view
online), or EPROMISC /UPEXPORT (create readable text file).
Typically the scan of your file base will take around 30 seconds
per 400 areas.
The user name should not have spaces replaced with underscores.
Eg PHILLIP MORGAN is valid for this function whereas
PHILLIP_MORGAN is not.
/UPEXPORT
After creating a list of files uploaded by a user
(UPLDLIST.DAT), you can create a plain ascii file that contains
that list that you can view yourself or send to the user who
uploaded the files.
For example, I use a questionaire to run a batch file that
passes the user name to EPROMISC /U=<user> and then runs
/UPEXPORT to convert the results to an ascii file and then fires
up a menu type 48 to download the file. In this fashion a user
can download a list of files they have uploaded to the BBS.
/VIEW
After creating a list of files uploaded by a user
(UPLDLIST.DAT), you can view the list of uploaded files by using
the EPROMISC /VIEW function.
The screen shows you the users name, the total number files
uploaded. The file name, area it currently resides in, how many
times it has been downloaded, size and file date are displayed
in the list.
Press SPACE to progress through the list if the user has
uploaded more than 15 files. When the end of the list is
reached press HOME to go to the top of the list. Press ESC at
any time to exit the view function.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
SAMPLE AGE GRAPH
----------------
Age Graph
----------------------------------------------------------------------------
11 - 15 |________
16 - 20 |____________________________________________
21 - 25 |____________________________________________________
26 - 30 |__________________________
31 - 35 |____________________
36 - 40 |__________________
41 - 45 |__________________
46 - 50 |________
51 - 55 |__
56 - 60 |____
61 - 65 |
66 - 70 |
+-------------------------------------------------------+
10 15 20 25 30 35
Percentage of userbase